Operation View
Digital Twin KIT
Based on the information provided in this kit, it is possible to run and program against an infrastructure of Digital Twins the Catena-X-way. This infrastructure empowers Data Consumers to consume the network's data as agreed with each Data Provider and facilitated by an Operating Company. They run central and decentral services that allow them to discover each other, exchange information and contextualize it according to a standardized semantics.
The APIs for digital twins are based on the specifications of the Asset Administration Shell (AAS) as defined in CX-0002.
Deployment
| Service Name | Description | Reference Implementation | Standardized in |
|---|---|---|---|
| Discovery Finder | A microservice resolving type of identifiers against a set of BPN-Discovery Servers. | Tractus-X Discovery Finder | CX - 0053 |
| BPN Discovery | A microservice resolving a particular assetId against the registered BPN of its owner. | Tractus-X BPN Discovery | CX - 0053 |
| EDC Discovery | A microservice that resolves a BPN against an EDC endpoint. | Tractus-X Portal including EDC Discovery API | CX - 0001 |
| Digital Twin Registry | A registry for digital twins, each digital twin providing the endpoints of its submodels. The registry is adhering to the AAS Registry API. | Tractus-X Digital Twin Registry | CX - 0002 |
| Submodel Server | The data source adhering to a subset of the Submodel API as defined in AAS Part-2 3.0. | FA³ST-Framework, Eclipse Basyx, AASX Server | CX - 0002 |
Setup Guide
Detailed guidance on setup of the abovementioned components can be found in the repositories of their linked reference implementations.
Notice
This work is licensed under the CC-BY-4.0.
- SPDX-License-Identifier: CC-BY-4.0
- SPDX-FileCopyrightText: 2023 Contributors of the Eclipse Foundation
- Source URL: https://github.com/eclipse-tractusx/tractusx-edc